I suggest to merge this by the end of July 2nd so that a new draft can be sent to IETF's document tracker. If possible, let's resolve #68 first, but I suggest that 68 should not block this PR.

Also after merging this PR, please mark a new release.

Should i wait with making a release a few hours to allow for more PRs ?

IMO the pending PR/issues are not a blocker for IETF submission. No plan on my side for more updates.

@michaelni, could you also mark a release at https://github.com/FFmpeg/FFV1/releases.

should that be called draft-niedermayer-cellar-ffv1-03 or draft-ietf-cellar-ffv1-03 ?
also what should i link to, last used https://datatracker.ietf.org/doc/draft-niedermayer-cellar-ffv1/02

Since it has become a Working Group document, it should be draft-ietf-cellar-ffv1-03.

done, thx

Blerg, when I go to upload to the doc tracker. I get this error:
Invalid revision (revision 00 is expected)

I suppose the version numbering resets when the doc is moved to a working group document. I can send a new PR to create draft-ietf-cellar-ffv1-00 but perhaps the commit of this PR should be dropped and the release should be renamed.

should i create a draft-ietf-cellar-ffv1-00 release ? or can you check first if its accepted now ?

The xml is now accepted and in The submission is pending approval by the group chairs. status.